Utility Management
The tables below contain descriptions of the Utility Management items that are part of the 2018.1 release of new world ERP.
To get software enhancements to our customers at the earliest possible availability, we provide new enhancements via MIU patches that can be downloaded and installed between releases. These enhancements are essentially “next release” enhancements delivered early. They are identified in the release notes with the previous release number and the “MIU” identifier (e.g., 2017.1 MIU).
For details on new features and enhancements to existing features, see "What's New in Utility Management."
| Account | |||
|---|---|---|---|
| Type | Description | Case Number(s) | Fix Version(s) | 
| Warranty | Enhancements have been made to improve the way payment plans apply payments against ongoing charges and plan installments. For more information, see Payment Plan Enhancements in 2018.1. | 5528795, 5527340, 5527333 | 2017.1 MIU | 
| Warranty | Some utilities may have a small number of accounts for which the overall balance is known and correctly displayed on most screens, while in other specific screens there exists a small discrepancy between the total balance and the balance displayed at the charge category/line-item detail level. This sometimes occurs due to software defects that have since been resolved. Enhancements have been made to correct this issue. For more information, see Correcting Bad Transaction Data. | NA | 2017.1 MIU | 
| Warranty | Fields related to the device Location were not being displayed completely. | 524184 | 2017.1 MIU | 
| Warranty | In some instances, new payment plans could not be created as a programming error was issued. | 5547031, 5529827 | 2017.1 MIU | 
| Warranty | If an account with only one meter was shared by water and sewer services, the transaction grid would show an icon instead of billed consumption. This has been corrected to look at the number of meters instead of the number of services. | 5543544 | 2017.1 MIU | 
| Warranty | When adding or maintaining a meter either directly or through work orders, the user can enter meter reader notes. There is a limit on the length of the notes, but no feedback was given to the user on that limit, the extra test was truncated without the users knowledge. Now the user receives feedback if they enter text that is too long. | 5547245, 5545899 | 2017.1 MIU | 
| Warranty | There are two types of account messages, customer and user. User messages are manually added and manually removed. For accounts with multiple user messages, when one was end-dated, they were all end-dated. | 5544064, 5546446, 5530642, 5546294 | 2017.1 MIU | 
| Warranty | Single installment payment plans were not working correctly. These represent extensions not payment plans. The customer is not agreeing to catch up to their current balance, they are agreeing only to pay a certain portion of their past due to avoid cut off. Single installments have been corrected to properly support this concept. | 5767201 | 2017.1 MIU | 
| Warranty | When creating single installment payment plans, the single installment was created with the plan start date rather than the due date entered by the user. | 5767201 | 2017.1 MIU | 
| Warranty | Meter Reader notes can now include numeric values. | 5776471 | 2017.1 MIU | 
| Warranty | For inactive accounts, the Customer Service Transaction screen was incorrectly showing NA in the consumption column. This has been corrected. | 5824319, 5893732, 5890751, 5886833, 5828619 | 2017.1 MIU | 
| Warranty | In some instances, the Transactions grid in Customer Service was displaying a consumption of NA even when the bill had consumption. This has been corrected. | 5977420, 5986895 | 2017.1 MIU | 
| Warranty | The option in Customer Service Transactions to reverse a payment would crash on payments that were converted from a legacy system. The page no longer crashes. Instead, it issues an error message indicating that converted transactions cannot be reversed. | 5995742 | 2017.1 MIU | 
| Warranty | Enhancements have been made to give administrators the option of including or excluding billing adjustment information from the Consumption Trend Report (UM) and Consumption Analysis page (eSuite). For more information, see Consumption Reporting & Billing Adjustments. | 5954331 | 2017.1 MIU | 
| Warranty | The Consumption Trend Report was incorrectly including adjustments that are not bill related. It now only includes bill related adjustments. | 5954331 | 2017.1 MIU | 
| Warranty | NSF processing and credit card enrollment were failing. This has been corrected. | 5954189, 5955726, 5957028, 5962603, 5963562, 5964766, 5962317, 5970158, 5970968 | 2017.1 MIU | 
| Warranty | The system can be configured to automatically create a Move Out when a Move In is created. In some rare instances, the Move Out account had historic Move Out bills from the conversion or a Move Out followed by a reinstate service. In these instances the automatic creation of a Move Out would fail. This has been corrected. | 5528467, 5716432, 5921255 | 2017.1 MIU | 
| Warranty | When a Move In was canceled, a subsequent Move In would require extra effort to assure the meters were accurately set to fuel any metered services. This fix is a data script to scrub old canceled move ins so the problem will not occur if fresh move ins are performed on the account. | 6059669 | 2017.1 MIU | 
| Warranty | Recurring credit cards using American Express cards showed as Discover card in the system. They charged out correctly against the correct card but showed incorrectly on the RCC enrollment page. | 6018990 | 2017.1 MIU | 
| Warranty | Accounts were missing meters on Move In. Data has been cleaned up. | 6059669 | 2017.1 MIU | 
| Adjustments | |||
|---|---|---|---|
| Type | Description | Case Number(s) | Fix Version(s) | 
| Warranty | In some very rare instances, when adjustment amounts were spread to the charge categories, a penny rounding issue could occur and result in an account that reports two slightly different balances in the system. | NA | 2017.1 MIU | 
| Billing | |||
|---|---|---|---|
| Type | Description | Case Number(s) | Fix Version(s) | 
| Product Improvement | The meter read history available on the bill export and printing can now include up to two years of history. | 523478 | 2017.1 MIU | 
| Product Improvement | The read history that can be included on the bill export and print now includes the billing date in addition to the meter read date. This can be more intuitive to the consumer as the billing date relates directly to the bills they received, whereas the meter read date may be significantly off from that date. | 525413 | 2017.1 MIU | 
| Product Improvement | The bill export now includes the email address of the primary account holder. | 5529308 | 2017.1 MIU | 
| Product Improvement | The following fields were added to the AMR Export: Meter Set Date, the complete Billing Address, and separate Customer First and Last Name. To see these fields in your export, your custom export must be modified. | NA | 2017.1 MIU | 
| Warranty | In some situations, the Unbilled Accounts report that is produced by the calculation process would incorrectly list accounts that should be billed. This happened when non-metered units were changed and future-dated. This has been corrected. | 5887135, 5701496, 5738551 | 2017.1 MIU | 
| Warranty | Accounts that have no rates associated with non-metered services now correctly show on the unbilled accounts report. | 523725 | 2017.1 MIU | 
| Warranty | On utility bills, the city, state, and zip code were on multiple lines in the XML data. This only affects customers using Tyler Froms. | NA | 2017.1 MIU | 
| Warranty | On refund checks, the nwERP XML data from UM and MB was returning the city, state, and zip code on multiple lines. This only affects customers using Tyler Froms. | NA | 2017.1 MIU | 
| Warranty | During the billing process, the Non-Billable Accounts report lists the accounts that are not configured correctly to bill. Previously, it was not including accounts that were not properly configured to bill non-metered services. It was changed to include those issues, but was producing false hits as well. These false hits were preventing some valid accounts from billing. This has been fixed. | 5656948, 5656941 | 2017.1 MIU | 
| Warranty | In some rare instances, posting exception bills would remove the non-metered units from random accounts in cycle bills. This has been corrected. | 5849192, 5727617 | 2017.1 MIU | 
| Warranty | The AMR export includes audit high and low reads. These are used by some AMR equipment to warn the reader if the read looks too large or too small. When the most recent read was an initialize/meter reset, these values were not set correctly and would not produce meaningful warnings. They are now correct. | 5547044 | 2017.1 MIU | 
| Warranty | A change was made to correct the high and low audit thresholds in the AMR export. In some instances that change caused the number of decimals on the audit to be incorrect. This has been corrected. | 5830017 | 2017.1 MIU | 
| Warranty | In some situations, the account address or meter test circle values were truncated in the exported data. This has been corrected. | 5955355, 6062561, 6042963 | 2017.1 MIU | 
| Delinquent Processing | |||
|---|---|---|---|
| Type | Description | Case Number(s) | Fix Version(s) | 
| Warranty | Delinquency processing has been enhanced to prevent simultaneous runs from different users. | 5540106, 5533990, 5523274 | 2017.1 MIU | 
| Warranty | Mailing addresses with commas or invalid zip-plus-4 values were breaking the delinquent statement print function. This has been corrected. | 5538452 | 2017.1 MIU | 
| Warranty | In certain very rare instances, the delinquent identify process would error out and would not identify any accounts. | 5530262 | 2017.1 MIU | 
| Warranty | If an NSF was performed on an account that was in an open bad debt batch, the bad debt batch would crash when you attempted to work with it. | 5588732, 5528219, 5661626, 56969585 | 2017.1 MIU | 
| Warranty | A device was not showing in device inventory. | 524172 | 2017.1 MIU | 
| Warranty | In certain very rare situations, running a delinquent event produced the error message "Failed to build statement history." | 5527021, 5525288 | 2017.1 MIU | 
| Warranty | The Bad Debt Report now properly honors the user’s security settings. | 5525356 | 2017.1 MIU | 
| Warranty | The Current Balance column has been added to the Bad Debt Edit Listing. | NA | 2017.1 MIU | 
| Warranty | The Bad Debt Edit Listing and Post Listing were not fitting on one page. | 6007127 | 2017.1 MIU | 
| Warranty | When sent to myReports rather than being displayed in the pop-up, every other page of the Bad Debt Edit report was blank. This has been corrected. | 6007127 | 2017.1 MIU | 
| Device Inventory | |||
|---|---|---|---|
| Type | Description | Case Number(s) | Fix Version(s) | 
| Warranty | A device was not showing in device inventory. | 524172 | 2017.1 MIU | 
| Forms | |||
|---|---|---|---|
| Type | Description | Case Number(s) | Fix Version(s) | 
| Warranty | In certain situations, some customers were receiving the error "Cannot insert the value NULL into column 'UTConsumptionHeaderID'". This error could occur on various forms. | 5523518, 5542420, 5542719, 5529634, 5542678, 5547489, 5535136, 5528551, 5528521 | 2017.1 MIU | 
| Warranty | When using the Echo form for exception bills, the bills were not printing in account number order. This has been corrected. | 5527945 | 2017.1 MIU | 
| Warranty | On utility bills, the customer mailing address was cut off when address lines 2/3 existed. Also, double ampersands appeared in the customer name. | NA | 2017.1 MIU | 
| Warranty | On UM refund checks, double ampersands displayed for Payee Name. | NA | 2017.1 MIU | 
| Warranty | If a field contained an ampersand (&), it would appear twice when pulled into Tyler Forms. | NA | 2017.1 MIU | 
| eSuite eUtilities | |||
|---|---|---|---|
| Type | Description | Case Number(s) | Fix Version(s) | 
| Software Improvement | Enhancements have been made to eSuite user authentication functionality. These enhancements give the user a more typical login experience, making it easier for them to log into eUtilities, create and save their sign-in credentials, and, should they ever forget them, recover their sign-in credentials. For more information, see eSuite Authentication. | NA | 2017.1 MIU | 
| Warranty | The eSuite landing page includes a balance at last billing value, and it associates a due date with that value. The value is now always the due date of the most recent bill. Previously, if a customer was in arrears, the due date was from the oldest outstanding bill. | 5578729, 5530114, 5549756, 5548828, 5549734, 5527325 | 2017.1 MIU | 
| Warranty | Enhancements have been made to give administrators the option of including or excluding billing adjustment information from the Consumption Trend Report (UM) and Consumption Analysis page (eSuite). For more information, see Consumption Reporting & Billing Adjustments. | 5954331 | 2017.1 MIU | 
| Warranty | In some instances, the due date would display incorrectly in eSuite. It now displays correctly. | 5930139, 5931559, 5971258 | 2017.1 MIU | 
| Receipts | |||
|---|---|---|---|
| Type | Description | Case Number(s) | Fix Version(s) | 
| Warranty | A confusing error message displayed when posting an ACH batch and no new cycles existed. | 5522920 | 2017.1 MIU | 
| Warranty | In some rare instances, the Total line at the bottom of the ACH file produced for the bank or clearing house was off by a penny from the actual sum of the detail drafts. This has been corrected. | 5923854 | 2017.1 MIU | 
| Warranty | If a consumer makes multiple payments on the same day, the IVR payment history API now reports them in the correct order. | 5772488 | 2017.1 MIU | 
| Reporting | |||
|---|---|---|---|
| Type | Description | Case Number(s) | Fix Version(s) | 
| Warranty | In some instances, the Account Status Report incorrectly listed the state on the address column of the report. | 5546953, 5523343, 5547603 | 2017.1 MIU | 
| Warranty | If there was a history of a billing item type, i.e., the same billing item billed at different times over the life of the account, then whenever the line item was displayed in the Billing Item Charges Report, it would be duplicated. The issue has been fixed. | 5670652 | 2017.1 MIU | 
| Warranty | 
                                                                            
 Note: Both items above should be installed to achieve the desired result.  | 
                                                                        5954331 | 2017.1 MIU | 
| Revenue Collections | |||
|---|---|---|---|
| Type | Description | Case Number(s) | Fix Version(s) | 
| Warranty | Clearing bad debt by taking payments in from Revenue Collections was not properly logging a transaction date in the bad debt ledger. | 5646420 | 2017.1 MIU | 
| Work Orders | |||
|---|---|---|---|
| Type | Description | Case Number(s) | Fix Version(s) | 
| Warranty | The work order result page and direct meter maintenance page no longer issue false errors on the length of the meter location entry. | 5629005 | 2017.1 MIU | 
| Warranty | The third party work order interface was not passing the primary customer name to the third party. This now works correctly. | NA | 2017.1 MIU |